Update "Short Lived Scheduled Task"#4152
Merged
Merged
Conversation
AndreiBanaru
requested review from
ljstella,
nasbench and
patel-bhavin
as code owners
July 7, 2026 09:49
nasbench
reviewed
Jul 7, 2026
nasbench
previously approved these changes
Jul 17, 2026
nasbench
left a comment
nasbench
left a comment
Contributor
There was a problem hiding this comment.
LGTM.
Re-generated the dataset to use XML instead and tested locally.
Reduced to Anomaly since the alert is not actionable by itself.
The CI is expected to fail on forks still.
nasbench
approved these changes
Jul 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I believe this detection was built on non-XML Windows Events. As such it does not work in modern environments.
Messagefield from| xmlkv Messagedoesn't really exist in XML events, nor does theTask_Nameform thetransactioncommand. I think would be better to look atobject_attrsand fetch theCommandfield- an analyst would be greatful, I believe.transactioncommand should be updated to "group" also bydest, not justTaskName.maxspan=30sshould be sufficient to replace theevaland thesearchevaluation section.